Prerecorded video experience container

ABSTRACT

A computer readable storage medium has stored thereon a prerecorded video experience container. The prerecorded video experience container includes a prerecorded video file that displays visual content, an executable experience which upon execution enables presentation of additional content associated with the prerecorded video file, and an interactive region of the prerecorded video file, wherein the interactive region of the prerecorded video file is associated with the executable experience such that a user interaction with the interactive region executes the executable experience. The prerecorded video file is displayed in response to a selection of the prerecorded video experience container. The executable experience associated with the prerecorded video file is executed in response to identifying an interaction with the interactive region. The additional content associated with the prerecorded video file is displayed in response to executing the executable experience.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/946,372, filed Jun. 18, 2020, which is a continuation of U.S. patentapplication Ser. No. 15/962,979, filed Apr. 25, 2018, the contents ofboth of which are incorporated herein by reference as if explicitly setforth.

BACKGROUND

Media files, such as audio and video files, are used in a variety ofenvironments for conveying many types of information. For example, mediafiles can be streamed or otherwise communicated over computer networks,allowing users to view and/or listen to the media content.Conventionally, video content is a one-directional medium such that acontent provider provides the video content to a user for viewing. Withthe advent of the Internet, the amount of video content available tousers has grown exponentially, as has the media platforms upon which thevideo content is available for viewing. Some media platforms haveattempted to provide some forms of interactivity with video content.However, conventional interactive video content suffers from manysignificant shortcomings.

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings, which are incorporated in and form a part ofthe Description of Embodiments, illustrate various embodiments of thesubject matter and, together with the Description of Embodiments, serveto explain principles of the subject matter discussed below. Unlessspecifically noted, the drawings referred to in this Brief Descriptionof Drawings should be understood as not being drawn to scale. Herein,like items are labeled with like item numbers.

FIG. 1 illustrates an example computer system upon which embodimentsdescribed herein be implemented.

FIG. 2 illustrates an example mobile electronic device upon whichembodiments described herein be implemented.

FIG. 3 illustrates an example network upon which embodiments describedherein may be implemented.

FIG. 4 illustrates a prerecorded video experience container creator, inaccordance with various embodiments.

FIG. 5 illustrates a prerecorded video experience container, inaccordance with various embodiments.

FIGS. 6A through 6F illustrate example screenshots of renderedprerecorded video files and defined interactive regions of prerecordedvideo experience containers, according to various embodiments.

FIG. 7 illustrates a flow diagram of an example method for creating aprerecorded video experience container, according to variousembodiments.

FIG. 8 illustrates a flow diagram of an example method for executing aprerecorded video experience container, according to variousembodiments.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to various embodiments of thesubject matter, examples of which are illustrated in the accompanyingdrawings. While various embodiments are discussed herein, it will beunderstood that they are not intended to limit to these embodiments. Onthe contrary, the presented embodiments are intended to coveralternatives, modifications and equivalents, which may be includedwithin the spirit and scope the various embodiments as defined by theappended claims. Furthermore, in this Description of Embodiments,numerous specific details are set forth in order to provide a thoroughunderstanding of embodiments of the present subject matter. However,embodiments may be practiced without these specific details. In otherinstances, well known methods, procedures, components, and circuits havenot been described in detail as not to unnecessarily obscure aspects ofthe described embodiments.

Notation and Nomenclature

Some portions of the detailed descriptions which follow are presented interms of procedures, logic blocks, processing and other symbolicrepresentations of operations on data bits within a computer memory.These descriptions and representations are the means used by thoseskilled in the data processing arts to most effectively convey thesubstance of their work to others skilled in the art. In the presentapplication, a procedure, logic block, process, or the like, isconceived to be one or more self-consistent procedures or instructionsleading to a desired result. The procedures are those requiring physicalmanipulations of physical quantities. Usually, although not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated in an electronic device.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the followingdiscussions, it is appreciated that throughout the description ofembodiments, discussions utilizing terms such as “displaying,”“receiving,” “assembling,” “displaying,” “executing,” “determining,”“using,” “accessing,” “selecting,” “customizing,” or the like, refer tothe actions and processes of an electronic device such as: a processor,a processor, an optical sensor, a sensor, a memory, a mobile electronicdevice, a sensor processing unit, a sensor processor, or the like, or acombination thereof. The electronic device manipulates and transformsdata represented as physical (electronic and/or magnetic) quantitieswithin the electronic device's registers and memories into other datasimilarly represented as physical quantities within the electronicdevice's memories or registers or other such information storage,transmission, processing, or display components.

Embodiments described herein may be discussed in the general context ofprocessor-executable instructions residing on some form ofnon-transitory processor-readable medium, such as program modules,executed by one or more computers or other devices. Generally, programmodules include routines, programs, objects, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. The functionality of the program modules may becombined or distributed as desired in various embodiments.

In the figures, a single block may be described as performing a functionor functions; however, in actual practice, the function or functionsperformed by that block may be performed in a single component or acrossmultiple components, and/or may be performed using hardware, usingsoftware, or using a combination of hardware and software. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the present disclosure. Also, the example mobile electronicdevice described herein may include components other than those shown,including well-known components.

The techniques described herein may be implemented in hardware,software, firmware, or any combination thereof, unless specificallydescribed as being implemented in a specific manner. Any featuresdescribed as modules or components may also be implemented together inan integrated logic device or separately as discrete but interoperablelogic devices. If implemented in software, the techniques may berealized at least in part by a non-transitory processor-readable storagemedium comprising instructions that, when executed, perform one or moreof the methods described herein. The non-transitory processor-readabledata storage medium may form part of a computer program product, whichmay include packaging materials.

The non-transitory processor-readable storage medium may comprise randomaccess memory (RAM) such as synchronous dynamic random access memory(SDRAM), read only memory (ROM), non-volatile random access memory(NVRAM), electrically erasable programmable read-only memory (EEPROM),FLASH memory, other known storage media, and the like. The techniquesadditionally, or alternatively, may be realized at least in part by aprocessor-readable communication medium that carries or communicatescode in the form of instructions or data structures and that can beaccessed, read, and/or executed by a computer or other processor.

The various illustrative logical blocks, modules, circuits andinstructions described in connection with the embodiments disclosedherein may be executed by one or more processors, such as one or moremotion processing units (MPUs), sensor processing units (SPUs),processor(s) or core(s) thereof, digital signal processors (DSPs),general purpose microprocessors, application specific integratedcircuits (ASICs), application specific instruction set processors(ASIPs), field programmable gate arrays (FPGAs), or other equivalentintegrated or discrete logic circuitry. The term “processor,” as usedherein may refer to any of the foregoing structures or any otherstructure suitable for implementation of the techniques describedherein. In addition, in some aspects, the functionality described hereinmay be provided within dedicated software modules or hardware modulesconfigured as described herein. Also, the techniques could be fullyimplemented in one or more circuits or logic elements. A general purposeprocessor may be a microprocessor, but in the alternative, the processormay be any conventional processor, controller, microcontroller, or statemachine. A processor may also be implemented as a combination ofcomputing devices, e.g., a combination of an SPU/MPU and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with an SPU core, MPU core, or any othersuch configuration.

Overview of Discussion

Discussion begins with a description of an example computer system uponwhich embodiments of the present invention may be implemented. Examplesof a prerecorded video experience container and systems for creating andusing a prerecorded video experience container are then described.Example operations of creating looping prerecorded video experiencecontainer are then described. Example operations of using a loopingprerecorded video experience container are then described.

In accordance with various embodiments, methods and systems for creatingand using a prerecorded video experience container are provided. In oneembodiment, in a method for creating a prerecorded video experiencecontainer, a prerecorded video file that displays visual content isreceived. In one embodiment, the prerecorded video file is a loopingprerecorded video file. An executable experience associated with theprerecorded video file is received, wherein the executable experienceupon execution enables presentation of additional content associatedwith the prerecorded video file. Identification of an interactive regionof the prerecorded video file is received, wherein the interactiveregion of the prerecorded video file is associated with the executableexperience such that a user interaction with the interactive regionexecutes the executable experience. The prerecorded video file, theexecutable experience, and the interactive region, are assembled into aprerecorded video experience container, wherein the prerecorded videoexperience container, when executed at an electronic device, displaysthe prerecorded video file and, responsive to identifying an interactionwith the interactive region, executes the executable experience.

In some embodiments, a computer readable storage medium has storedthereon a prerecorded video experience container. The prerecorded videoexperience container includes a prerecorded video file that displaysvisual content, an executable experience which upon execution enablespresentation of additional content associated with the prerecorded videofile, and an interactive region of the prerecorded video file, whereinthe interactive region of the prerecorded video file is associated withthe executable experience such that a user interaction with theinteractive region executes the executable experience. The prerecordedvideo file is displayed in response to a selection of the prerecordedvideo experience container. The executable experience associated withthe prerecorded video file is executed in response to identifying aninteraction with the interactive region. The additional contentassociated with the prerecorded video file is displayed in response toexecuting the executable experience.

Video content is a useful medium by which to convey visual informationto a user. Conventionally, video content is a one-directional mediumsuch that a content provider provides the video content to a user forviewing. With the advent of the Internet, the amount of video contentavailable to users has grown exponentially, as has the media platformsupon which the video content is available for viewing. Some mediaplatforms have attempted to provide some forms of interactivity withvideo content. However, conventional interactive video content suffersfrom many significant shortcomings.

For instance, conventional interactive video content is typicallyplatform dependent. The creation of such conventional interactive videocontent requires that the content be tailored to the particular platformupon which the content is to be played and presented. For each platformthat a content provider desires to provide interactive video content, adifferent version of the same interactive content must be created. Assuch, creating multiple versions of the same interactive content forpresentation on different platforms requires duplicative work,increasing computing resource requirements, labor, costs, and time.Also, for each platform for which interactive video content is created,knowledge of the operations of each platform is required. As such,conventional interactive video content creation tends to be ad hoc andpiecemeal, as well as proprietary, as there is no complete solutionavailable. As the number of platforms with substantial user bases islarge and increasing, the costs associated with generating interactivevideo content will continue to grow.

Moreover, conventional interactive video content is generally forpresentation within the platform for which it is created. In otherwords, conventional interactive video content is not freelytransportable or usable outside of the platforms used for its creation.Not only must content creators create the interactive video content formultiple platforms, users must have access to or execute a platform forwhich the interactive video content was created to access and/orinteract with the interactive video content. These limitations aresignificant in reaching desired users of the interactive video content.Moreover, if interactive video content is created for a single user or agroup of users, all users must have access to the platform for which theinteractive video content is created. Such limitations on the access tointeractive content place technical limitations on the impacted users,requiring users to locate and/or install particular applications oncomputing devices for accessing the interactive content.

Furthermore, conventional interactive video content is typicallyrudimentary in the type of interactivity provided. For example, whileinteracting with a piece of video content (e.g., by clicking on thevideo content via a mouse), a user may be directed to a website, thevideo content itself includes no information regarding the control,presentation, or customization of any additional content. Anycustomization, if available, is under the control of the platform forwhich the content was created, and is not directly related to the videocontent itself. In particular, the customization is only applicable tothe platform for which the content was created.

Various embodiments described herein provide a transportable prerecordedvideo experience container that includes a looping prerecorded videofile and an executable experience in a single container for an improvedsolution of providing interactive video content. The prerecorded videoexperience container is platform agnostic, and can provide interactivitywithout requiring access to a particular platform or application. Thisimproves the efficiency and usefulness of interactive video content byproviding a transportable prerecorded video experience containerincluding the executable experience for presenting additional contentrelated to the looping prerecorded video. The prerecorded videoexperience container is transportable over any communication medium, andcan be used in concert with many different applications, withoutrequiring a particular platform. In particular, embodiments describedherein provide a platform agnostic solution for providing interactivevideo content. In various embodiments, the prerecorded video experiencecontainer is freely transmissible (e.g., via email, messagingapplications, web pages, social networks, etc.)

The prerecorded video experience container described herein includes avideo file, an executable experience associated with the video file, andinformation enabling interactivity of the video file for enabling theexecutable experience within a single container (e.g., a softwarecontainer or a software package). The prerecorded video experiencecontainer is transmissible through any networked transmission medium,and can include and/or execute applications in response to theinteractivity. For example, the prerecorded video experience containercan be sent as an email attachment, can be sent as an attachment withina messaging application (e.g., Apple's iMessage, Android Messages,Facebook Messenger, etc.), or can be imbedded within a web page or webapplication (e.g., as an Iframe).

Embodiments described herein provide for the creation of a prerecordedvideo experience container. A prerecorded video file displaying visualcontent is received. In some embodiments, the prerecorded video file isreceived from a library of prerecorded video files (e.g., maintained bya service hosting prerecorded video files) over a network connection. Inother embodiments, the prerecorded video file is located on a localcomputer. It should be appreciated that the prerecorded video file canbe received from any source, and can have any creator. In someembodiments, the prerecorded video file is a looping video file (e.g.,automatically restarts after completing a playback). The loopingfunctionality can be implemented within the prerecorded video fileitself, within a prerecorded video experience container, or withinanother application on the playback device. Moreover, it should beappreciated that the prerecorded video file can be any length. In someembodiments, e.g., where the prerecorded video file is looping, theprerecorded video file is less than 30 seconds in length.

Embodiments described herein pertain to prerecorded video experiencecontainer including a prerecorded video file. In one embodiment, theprerecorded video file is a Graphics Interchange Format (GIF) file.While embodiments described herein pertain to GIF files, it should beappreciated that other types of prerecorded media files, such as othertypes of video files, can be used herein. Moreover, it should beappreciated that any type of video file format can be used in accordancewith the described embodiments, including but not limited to GIF, WebM,WebP, MPEG-4 (MP4), Animated Portable Network Graphics (APNG), MotionJPEG, Flash video (FLV), Windows Media video, M4V, etc. It should beappreciated that the prerecorded media file can be looped (e.g., via aHTML 5 video element or Flash video element) to automatically repeat.

The prerecorded video experience container also includes an executableexperience associated with the prerecorded video file. The executableexperience provides for the presentation of additional contentassociated with the prerecorded video file. The executable experiencemay include one or more media files, applications, instructions forexecuting an application, and instructions for controlling operation ofan application. Example media files include, without limitation: videofiles, audio files, images, e-books, etc. Example applications includegames, media players (e.g., for playing a media file of the executableexperience), web applications, etc. Example instructions for executingan application include instructions to execute a messaging application,a media player application, a web browser, etc. Example instructions forcontrolling operation of an application include commands for interactingwith a media player, web application. It should be appreciated that theprerecorded video experience container can include any number ofexecutable experiences that are executable responsive to interactionswith different interactive regions of the rendered prerecorded videofile, or responsive to other customization factors.

An executable experience is executed in response to a user interactionwith the prerecorded video file during playback. An interaction caninclude a cursor selection, a finger touch (e.g., at a touch screendisplay), gestures, etc. In some embodiments, at least one interactiveregion on the rendered prerecorded video file is defined and includedwithin the prerecorded video experience container. An interactive regionoverlays or is superimposed over the prerecorded video file duringplayback and defines areas of the display for receiving theinteractions. Any number of interactive regions can be defined for aprerecorded video file. In some embodiments, different interactiveregions are for executing different executable experiences. Aninteractive region or regions can be superimposed over an entirerendered prerecorded video file, or an interactive region or regions canbe superimposed over a portion of the rendered prerecorded video file,leaving non-interactive portions of the rendered prerecorded video file.

In some embodiments, the prerecorded video experience container alsoincludes at least one customization factor associated with theexecutable experience, wherein the at least one customization factorcustomizes the additional content upon execution of the executableexperience. The customization factor can include at least one of,without limitation: a location, a user, a time day, and a date. Forinstance, where a prerecorded video experience container includes morethan one executable experience, a particular executable experience canbe selected for presentation partly based on the customization factor.For example, a particular executable experience can be presented basedon a time of day (e.g., based on a system clock of the renderingelectronic device). A prerecorded video experience container can includetwo prerecorded video files, one for rendering during a first timeperiod (e.g., 9:00 AM through 5:00 PM), and a second for renderingduring a second time period (e.g., 5:00 PM through 9:00 AM). Asdescribed below, the customization factors can be used to tailor thepresentation of additional content according to day, date, time,location, users, etc.

In some embodiments, the executable experience is tailored by accessinga user profile of the user operating the rendering electronic device.The user profile can be stored on the electronic device, or accessed viathe electronic device. The user profile can include various types ofidentifying information of various granularities, including withoutlimitation: age, birthdate, gender, interests, race/ethnicity, languagespoken/understood, etc. In various embodiments, a prerecorded videoexperience container can include a plurality of executable experiences,where an interaction with the prerecorded video file causes presentationof one of the executable experiences based on the user profile.

Embodiments described herein provide a prerecorded video experiencecontainer that is self-contained and transmittable. The prerecordedvideo experience container includes all information needed forpresenting additional content. In some embodiments, the prerecordedvideo experience container includes multiple executable experiences thatare customized for presentation based on customization factors withinthe prerecorded video experience container and/or a user profile of theuser operating the rendering electronic device. The describedembodiments improve the efficiency and usefulness of interactive videocontent by providing a transportable prerecorded video experiencecontainer including the executable experience for presenting additionalcontent related to the prerecorded video file.

Example Computer System and Mobile Electronic Device

Turning now to the figures, FIG. 1 is a block diagram of an examplecomputer system 100 upon which embodiments of the present invention canbe implemented. FIG. 1 illustrates one example of a type of computersystem 100 (e.g., a computer system) that can be used in accordance withor to implement various embodiments which are discussed herein.

It is appreciated that computer system 100 of FIG. 1 is only an exampleand that embodiments as described herein can operate on or within anumber of different computer systems including, but not limited to,general purpose networked computer systems, embedded computer systems,mobile electronic devices, smart phones, server devices, client devices,various intermediate devices/nodes, stand alone computer systems, mediacenters, handheld computer systems, multi-media devices, and the like.In some embodiments, computer system 100 of FIG. 1 is well adapted tohaving peripheral tangible computer-readable storage media 102 such as,for example, an electronic flash memory data storage device, a floppydisc, a compact disc, digital versatile disc, other disc based storage,universal serial bus “thumb” drive, removable memory card, and the likecoupled thereto. The tangible computer-readable storage media isnon-transitory in nature.

Computer system 100 of FIG. 1 includes an address/data bus 104 forcommunicating information, and a processor 106A coupled with bus 104 forprocessing information and instructions. As depicted in FIG. 1, computersystem 100 is also well suited to a multi-processor environment in whicha plurality of processors 106A, 106B, and 106C are present. Conversely,computer system 100 is also well suited to having a single processorsuch as, for example, processor 106A. Processors 106A, 106B, and 106Cmay be any of various types of microprocessors. Computer system 100 alsoincludes data storage features such as a computer usable volatile memory108, e.g., random access memory (RAM), coupled with bus 104 for storinginformation and instructions for processors 106A, 106B, and 106C.Computer system 100 also includes computer usable non-volatile memory110, e.g., read only memory (ROM), coupled with bus 104 for storingstatic information and instructions for processors 106A, 106B, and 106C.Also present in computer system 100 is a data storage unit 112 (e.g., amagnetic or optical disc and disc drive) coupled with bus 104 forstoring information and instructions. Computer system 100 also includesan alphanumeric input device 114 including alphanumeric and functionkeys coupled with bus 104 for communicating information and commandselections to processor 106A or processors 106A, 106B, and 106C.Computer system 100 also includes a cursor control device 116 coupledwith bus 104 for communicating user input information and commandselections to processor 106A or processors 106A, 106B, and 106C. In oneembodiment, computer system 100 also includes a display device 118coupled with bus 104 for displaying information.

Referring still to FIG. 1, display device 118 of FIG. 1 may be a liquidcrystal device (LCD), light emitting diode display (LED) device, cathoderay tube (CRT), plasma display device, a touch screen device, or otherdisplay device suitable for creating graphic images and alphanumericcharacters recognizable to a user. Cursor control device 116 allows thecomputer user to dynamically signal the movement of a visible symbol(cursor) on a display screen of display device 118 and indicate userselections of selectable items displayed on display device 118. Manyimplementations of cursor control device 116 are known in the artincluding a trackball, mouse, touch pad, touch screen, joystick orspecial keys on alphanumeric input device 114 capable of signalingmovement of a given direction or manner of displacement. Alternatively,it will be appreciated that a cursor can be directed and/or activatedvia input from alphanumeric input device 114 using special keys and keysequence commands. Computer system 100 is also well suited to having acursor directed by other means such as, for example, voice commands. Invarious embodiments, alphanumeric input device 114, cursor controldevice 116, and display device 118, or any combination thereof (e.g.,user interface selection devices), may collectively operate to provide agraphical user interface (GUI) 130 under the direction of a processor(e.g., processor 106A or processors 106A, 106B, and 106C). GUI 130allows user to interact with computer system 100 through graphicalrepresentations presented on display device 118 by interacting withalphanumeric input device 114 and/or cursor control device 116.

Computer system 100 also includes an I/O device 120 for couplingcomputer system 100 with external entities. For example, in oneembodiment, I/O device 120 is a modem for enabling wired or wirelesscommunications between computer system 100 and an external network suchas, but not limited to, the Internet. In one embodiment, I/O device 120includes a transmitter. Computer system 100 may communicate with anetwork by transmitting data via I/O device 120.

Referring still to FIG. 1, various other components are depicted forcomputer system 100. Specifically, when present, an operating system122, applications 124, modules 126, and data 128 are shown as typicallyresiding in one or some combination of computer usable volatile memory108 (e.g., RAM), computer usable non-volatile memory 110 (e.g., ROM),and data storage unit 112. In some embodiments, all or portions ofvarious embodiments described herein are stored, for example, as anapplication 124 and/or module 126 in memory locations within RAM 108,computer-readable storage media within data storage unit 112, peripheralcomputer-readable storage media 102, and/or other tangiblecomputer-readable storage media.

Turning now FIG. 2, a block diagram of an example mobile electronicdevice 200 is shown. As will be appreciated, mobile electronic device200 may be implemented as a device or apparatus, such as a handheldmobile electronic device, that can be moved in space by a human user.That is, mobile electronic device 200 is small enough to be held in thehand of a human user, in various embodiments. For example, such a mobileelectronic device may be, without limitation, a mobile telephone phone(e.g., smartphone, cellular phone, a cordless phone running on a localnetwork, or any other cordless telephone handset), a wired telephone(e.g., a phone attached by a wire), a personal digital assistant (PDA),a video game player, video game controller, a navigation device, anactivity or fitness tracker device (e.g., bracelet, clip, band, orpendant), a smart watch or other wearable device, a mobile internetdevice (MID), a personal navigation device (PND), a digital stillcamera, a digital video camera, a portable music player, a portablevideo player, a portable multi-media player, a remote control, aheadset, or a combination of one or more of these devices.

As depicted in FIG. 2, mobile electronic device 200 may include aprocessor 210, a bus 220, a memory 230, at least one optical sensor 235,and a display 240. Some embodiments of mobile electronic device 200 mayfurther include one or more of an interface 250, a transceiver 260 (alldepicted in dashed lines), a location sensor 270, and/or othercomponents. In various embodiments, electrical power for mobileelectronic device 200 is provided by a mobile power source such as abattery, when not being actively charged.

Processor 210 can be one or more microprocessors, central processingunits (CPUs), DSPs, general purpose microprocessors, ASICs, ASIPs, FPGAsor other processors which run software programs or applications, whichmay be stored in memory 230, associated with the functions andcapabilities of mobile electronic device 200.

Bus 220 may be any suitable bus or interface to include, withoutlimitation, a peripheral component interconnect express (PCIe) bus, auniversal serial bus (USB), a universal asynchronousreceiver/transmitter (UART) serial bus, a suitable advancedmicrocontroller bus architecture (AMBA) interface, an Inter-IntegratedCircuit (I2C) bus, a serial digital input output (SDIO) bus, a serialperipheral interface (SPI) or other equivalent. In the embodiment shown,processor 210, memory 230, display 240, interface 250, transceiver 260,and other components of mobile electronic device 200 may be coupledcommunicatively through bus 220 in order to exchange commands and data.Depending on the architecture, different bus configurations may beemployed as desired. For example, additional buses may be used to couplethe various components of mobile electronic device 200, such as by usinga dedicated bus between processor 210 and memory 230.

Memory 230 can be any suitable type of memory, including but not limitedto electronic memory (e.g., read only memory (ROM), random accessmemory, or other electronic memory), hard disk, optical disk, or somecombination thereof. Multiple layers of software can be stored in memory230 for use with/operation upon processor 210. For example, an operatingsystem layer can be provided for mobile electronic device 200 to controland manage system resources in real time, enable functions ofapplication software and other layers, and interface applicationprograms with other software and functions of mobile electronic device200. Similarly, a user experience system layer may operate upon or befacilitated by the operating system. The user experience system maycomprise one or more software application programs such as menunavigation software, games, device function control, gesturerecognition, image processing or adjusting, voice recognition,navigation software, communications software (such as telephony orwireless local area network (WLAN) software), and/or any of a widevariety of other software and functional interfaces for interaction withthe user can be provided. In some embodiments, multiple differentapplications can be provided on a single mobile electronic device 200,and in some of those embodiments, multiple applications can runsimultaneously as part of the user experience system. In someembodiments, the user experience system, operating system, and/or theprocessor 210 may operate in a low-power mode (e.g., a sleep mode) wherevery few instructions are processed. Such a low-power mode may utilizeonly a small fraction of the processing power of a full-power mode(e.g., an awake mode) of the processor 210.

Optical sensor 235 may comprise, without limitation: a video capturedevice, a camera, and infrared camera, or other type of optical sensorfor capturing a video of a person, an object, and/or a scene. It shouldbe appreciated that mobile electronic device 200 may include more thanone optical sensor. In one example, optical sensor 235 is a back-sideoptical sensor (e.g., rear-facing camera) and optical sensor 238 is afront-side optical sensor (e.g., front-facing camera).

Display 240, may be a liquid crystal device, (organic) light emittingdiode device, or other display device suitable for creating and visiblydepicting graphic images and/or alphanumeric characters recognizable toa user. Display 240 may be configured to output images viewable by theuser and may additionally or alternatively function as a viewfinder forcamera. Display 240 is configured to display video captured at opticalsensor 235 (and optical sensor 238, when included).

Interface 250, when included, can be any of a variety of differentdevices providing input and/or output to a user, such as audio speakers,touch screen integrated with display 240, real or virtual buttons,joystick, slider, knob, printer, scanner, computer network I/O device,other connected peripherals and the like.

Transceiver 260, when included, may be one or more of a wired orwireless transceiver which facilitates receipt of data at mobileelectronic device 200 from an external transmission source andtransmission of data from mobile electronic device 200 to an externalrecipient. By way of example, and not of limitation, in variousembodiments, transceiver 260 comprises one or more of: a cellulartransceiver, a wireless local area network transceiver (e.g., atransceiver compliant with one or more Institute of Electrical andElectronics Engineers (IEEE) 802.11 specifications for wireless localarea network communication), a wireless personal area networktransceiver (e.g., a transceiver compliant with one or more IEEE 802.15specifications for wireless personal area network communication), and awired a serial transceiver (e.g., a universal serial bus for wiredcommunication).

Location sensor 270, when included, may be a sensor for determining alocation of mobile electronic device 200, such as a navigation satellitesystem sensor such as a Global Navigation Satellite System (GNSS)receiver (e.g., Global Positioning System (GPS) sensor) and/or othercomponents configured to determine the location of mobile electronicdevice 200 from external radio signals. It is noted that thefunctionality of location sensor 270 may be implemented by processor210.

FIG. 3 illustrates an example communication network 340 upon whichembodiments described herein may be implemented. FIG. 3 illustrateselectronic device 310, electronic device 320, and computer system 330,all of which are communicatively coupled via network 340. It should beappreciated that mobile electronic device 310, electronic device 320,and remote computer system 330, may be implemented as a computer system100 or mobile electronic device 200, and/or include any combination ofthe components of computer system 100 or mobile electronic device 200.In some embodiments, mobile electronic device 310 and electronic device320 are mobile electronic devices (e.g., smart phones) includingmessaging applications for communicating electronic messages via agraphical user interface.

In accordance with various embodiments, electronic devices 310 and 320are capable of transmitting and receiving electronic messages includingmedia files. Electronic devices 310 and 320 may be associated with aparticular user. For example, a first user, may be associated withmobile electronic device 310 and a second user, may be associated withelectronic device 320. In one embodiment, remote computer system 330includes a prerecorded video experience container creator 400 forcreating prerecorded video experience container.

Example Creation and Use of a Prerecorded Video Experience Container

FIG. 4 illustrates a prerecorded video experience container creator 400,in accordance with various embodiments. Prerecorded video experiencecontainer creator 400 is configured to provide for the creation ofprerecorded video experience containers. In one embodiment, prerecordedvideo experience container creator 400 includes prerecorded video filereceiver 410, executable experience receiver 420, interactive regionidentification receiver 430, and prerecorded video experience containerassembler 450. In some embodiments, prerecorded video experiencecontainer creator 400 also includes customization factor receiver 440.

It should be appreciated that prerecorded video experience containercreator 400 can be implemented as hardware, software, or any combinationthereof. For example, prerecorded video experience container creator 400may be executed by computer system 100 of FIG. 1. In some embodiments,individual components of prerecorded video experience container creator400 may be distributed over multiple computing devices. For example,with reference to FIG. 3, prerecorded video experience container creator400 may access and/or receive different components of a prerecordedvideo experience container from remote computer systems communicativelycoupled to network 340 (e.g., a library of prerecorded video files or alibrary of executable experiences).

Prerecorded video file receiver 410 is configured to receive aprerecorded video file 412 for displaying visual content. In someembodiments, the prerecorded video file 412 is received from a libraryof prerecorded video files (e.g., maintained by a service hostingprerecorded video files) over a network connection (e.g., network 340).In other embodiments, the prerecorded video file 412 is located on alocal computer. It should be appreciated that the prerecorded video file412 can be received from any source, and can have any creator. In someembodiments, the prerecorded video file 412 is a looping video file(e.g., automatically restarts after completing a playback). The loopingfunctionality can be implemented within prerecorded video file 412itself, within a prerecorded video experience container, or withinanother application on the playback device. Moreover, it should beappreciated that the prerecorded video file 412 can be any length. Insome embodiments, e.g., where the prerecorded video file 412 is looping,the prerecorded video file 412 is less than 30 seconds in length.

In one embodiment, the prerecorded video file is a Graphics InterchangeFormat (GIF) file. While embodiments described herein pertain to GIFfiles, it should be appreciated that other types of prerecorded mediafiles, such as other types of video files, can be used herein. Moreover,it should be appreciated that any type of video file format can be usedin accordance with the described embodiments, including but not limitedto GIF, WebM, WebP, MPEG-4 (MP4), Animated Portable Network Graphics(APNG), Motion JPEG, Flash video (FLV), Windows Media video, M4V, etc.It should be appreciated that the prerecorded media file can be looped(e.g., via a HTML 5 video element or Flash video element) toautomatically repeat.

Executable experience receiver 420 is configured to receive one or moreexecutable experiences 422 associated with the prerecorded video file412. The executable experience(s) 422 provides for the presentation ofadditional content associated with the prerecorded video file 412. Theexecutable experience 422 may include one or more media files,applications, instructions for executing an application, andinstructions for controlling operation of an application. Example mediafiles include, without limitation: video files, audio files, images,e-books, etc. Example applications include games, media players (e.g.,for playing a media file of the executable experience), webapplications, etc. Example instructions for executing an applicationinclude instructions to execute a messaging application, a media playerapplication, a web browser, etc. Example instructions for controllingoperation of an application include commands for interacting with amedia player, web application. It should be appreciated that theprerecorded video experience container can include any number ofexecutable experiences 422 that are executable responsive tointeractions with different interactive regions of the renderedprerecorded video file 412, or responsive to other customizationfactors.

An executable experience is executed in response to a user interactionwith the prerecorded video file during playback. An interaction caninclude a cursor selection, a finger touch (e.g., at a touch screendisplay), gestures, etc. In some embodiments, at least one interactiveregion on the rendered prerecorded video file is defined and includedwithin the prerecorded video experience container.

Interactive region identification receiver 430 is configured to receiveinformation defining one or more interactive regions for receivinginteractions with the prerecorded video file 412. An interaction caninclude a cursor selection, a finger touch (e.g., at a touch screendisplay), gestures, etc. In some embodiments, at least one interactiveregion on the rendered prerecorded video file is defined and includedwithin the prerecorded video experience container. An interactive regionoverlays or is superimposed over the prerecorded video file 412 duringplayback and defines areas of the display for receiving theinteractions. Any number of interactive regions can be defined for aprerecorded video file. In some embodiments, different interactiveregions are for executing different executable experiences. Aninteractive region or regions can be superimposed over an entirerendered prerecorded video file, or an interactive region or regions canbe superimposed over a portion of the rendered prerecorded video file,leaving non-interactive portions of the rendered prerecorded video file.

In some embodiments, prerecorded video experience container creator 400also includes customization factor receiver 440. Customization factorreceiver 440 is configured to receive at least one customization factor442 for customizing the additional content upon execution of theexecutable experience. The customization factor 442 can include at leastone of, without limitation: a location, a user, a time day, and a date.For instance, where a prerecorded video experience container includesmore than one executable experience 422, a particular executableexperience can be selected for presentation partly based on thecustomization factor 442. For example, a particular executableexperience can be presented based on a time of day (e.g., based on asystem clock of the rendering electronic device). A prerecorded videoexperience container can include two prerecorded video files, one forrendering during a first time period (e.g., 9:00 AM through 5:00 PM),and a second for rendering during a second time period (e.g., 5:00 PMthrough 9:00 AM). The customization factors can be used to tailor thepresentation of additional content according to day, date, time,location, users, etc.

In some embodiments, the executable experience 422 is tailored byaccessing a user profile of the user operating the rendering electronicdevice. The user profile can be stored on the electronic device, oraccessed via the electronic device. The user profile can include varioustypes of identifying information of various granularities, includingwithout limitation: age, birthdate, gender, interests, race/ethnicity,language spoken/understood, etc. In various embodiments, a prerecordedvideo experience container can include a plurality of executableexperiences, where an interaction with the prerecorded video file causespresentation of one of the executable experiences based on the userprofile.

Prerecorded video experience container assembler 450 is configured toassemble prerecorded video file 412, one or more exactable experiences422, and one or more interactive region identifications 432 into aprerecorded video experience container 452. In one embodiment,prerecorded video experience container assembler 450 is also configuredto include the customization factors 442 into prerecorded videoexperience container 452.

FIG. 5 illustrates a prerecorded video experience container 500, inaccordance with various embodiments. Prerecorded video experiencecontainer 500 includes a prerecorded video file 510 that displays visualcontent, an executable experience 520 which upon execution enablespresentation of additional content associated with the prerecorded videofile 510, and an interactive region 530 of the prerecorded video file510, wherein the interactive region 530 of the prerecorded video file510 is associated with the executable experience 520 such that a userinteraction with the interactive region 530 executes the executableexperience 520. The prerecorded video file 510 is displayed in responseto a selection of the prerecorded video experience container 500. Theexecutable experience 520 associated with the prerecorded video file 510is executed in response to identifying an interaction with theinteractive region 530. The additional content associated with theprerecorded video file 510 is displayed in response to executing theexecutable experience.

Embodiments described herein provide a prerecorded video experiencecontainer 500 that is self-contained and transmittable. The prerecordedvideo experience container 500 includes all information needed forpresenting additional content. In some embodiments, the prerecordedvideo experience container 500 includes multiple executable experiences520 that are customized for presentation based on customization factors540 within the prerecorded video experience container 500 and/or a userprofile of the user operating the rendering electronic device. Thedescribed embodiments improve the efficiency and usefulness ofinteractive video content by providing a transportable prerecorded videoexperience container including the executable experience for presentingadditional content related to the prerecorded video file.

FIGS. 6A through 6F illustrate example screenshots of renderedprerecorded video files and defined interactive regions of prerecordedvideo experience containers, according to various embodiments. Forexample, FIGS. 6A through 6F may illustrate a view presented to acreator of a prerecorded video experience container during creation ofthe container. Using a graphical user interface, the creator may defineone or more interactive regions for receiving a user interaction. Itshould be appreciated that an interaction is defined by the particulardevice or computer system with which a viewer is interacting (e.g., atouch screen on a smart phone or a mouse click with a desktop computer).FIGS. 6A through 6F also illustrate example screenshots of renderedprerecorded video files as presented to a user, where the interactiveregion is defined yet not visible.

With reference to FIG. 6A, prerecorded video file 600 is displayed,where prerecorded video file shows a video of a game of checkers beingplayed. Interactive region 602 is defined, such that a user interactionwith interactive region 602 causes the execution of an executableexperience related to prerecorded video file 600. For example, theexecutable experience may include a checkers video game that is executedin response to detecting the user interaction. In one embodiment, thecheckers video game is a self-contained executable included within theprerecorded video experience container along with prerecorded video file600 and defined interactive region 602.

FIG. 6B illustrates a screen shot of prerecorded video file 620, whereprerecorded video file shows a video of a family walking down a dirtroad. Interactive regions 622 a-d are defined, where each interactiveregion 622 a-d is associated with a particular family member.Interaction with one of interactive regions 622 a-d causes the executionof an executable experience associated with prerecorded video file 620and associated with the selected interactive region. For example, theexecutable experience may include automatically initiating a voice ormessaging application with the person identified by the particularinteractive region. For instance, a user interaction with interactiveregion 622 d can open up a messaging application (e.g., Facetime oriMessage) and automatically initiate a call or message with the personidentified by interactive region 622 d.

FIG. 6C illustrates a screen shot of prerecorded video file 640, whereprerecorded video file shows a video of the making of a coffee-relatedbeverage. Interactive region 642 is defined. Interaction withinteractive regions 642 causes the execution of an executable experiencerelated to prerecorded video file 640. For example, the executableexperience may include presenting a coupon for a coffee-related beverageat particular store, presenting a video on the making of coffee, or avideo game that presents a coupon redeemable at a particular storedepending on the user's performance in the video game.

In some embodiments, the prerecorded video experience containerincluding prerecorded video file 640 includes at least one definedcustomization factor. For example, if an interaction with interactiveregion 642 is detected during business hours of a business associatedwith the prerecorded video file 640, a coupon is presented, where if aninteraction with interactive region 642 is detected outside of businesshours of the business associated with the prerecorded video file 640, avideo on the making of coffee is presented. As such, the prerecordedvideo experience container includes different executable experiencesthat are initiated depending, at least in part, on a customizationfactor.

FIG. 6D illustrates a screen shot of prerecorded video file 660, whereprerecorded video file shows a video of roller coaster at a theme park.Interactive region 662 is defined. Interaction with interactive regions662 causes the execution of an executable experience related toprerecorded video file 660. For example, the executable experience mayinclude presenting a coupon for the theme park, executing a video gameassociated with roller coasters, presenting a video about the themepark, etc.

FIG. 6E illustrates a screen shot of prerecorded video file 680, whereprerecorded video file shows a video of two young adults wearing trendyclothing. Interactive regions 682 a-c are defined, where eachinteractive region 682 a-c is associated with a particular item ofclothing. Interaction with one of interactive regions 682 a-c causes theexecution of an executable experience associated with prerecorded videofile 680 and associated with the selected interactive region. Forexample, the executable experience may include automatically presentinginformation (e.g., opening a web page, opening a shopping application,etc.) for purchasing the selected item of clothing. For instance, a userinteraction with interactive region 682 a can open up an applicationenabling purchase of the selected hat.

FIG. 6F illustrates a screen shot of prerecorded video file 690, whereprerecorded video file shows a video of a rock band performing.Interactive regions 692 a-e are defined, where each interactive region692 a-e is associated with a selectable region. Specifically,interactive regions 692 a-d are associated with particular band members,and interactive region 692 e is associated with the whole band.Interaction with one of interactive regions 692 a-e causes the executionof an executable experience associated with prerecorded video file 690and associated with the selected interactive region. For example, theexecutable experience may include automatically presenting informationabout the selected band member (e.g., a biographical video or aninterview) or band (open an application for purchasing concert ticketsfor the band). In another example, interaction with interactive region692 e causes the execution of different executable experiences based ona customization factor (e.g., location). If the location of the userdevice is physically and temporally proximate a performance by the band(as defined by the creator of the prerecorded video experiencecontainer), an application for purchasing a ticket to the performance ispresented. Alternatively, if the user device is not located near afuture performance, a video of the band performing can be presented. Inthe present example, the instructions for purchasing tickets to theperformance and the video are included within the prerecorded videoexperience container.

Example Methods of Operation of Creating and Using a Prerecorded VideoExperience Container

FIG. 7 illustrates a flow diagram 700 of an example method for creatinga prerecorded video experience container, according to variousembodiments. Procedures of this method may be described with referenceto elements and/or components of various figures described herein. It isappreciated that in some embodiments, the procedures may be performed ina different order than described, that some of the described proceduresmay not be performed, and/or that one or more additional procedures tothose described may be performed. Flow diagram 700 includes someprocedures that, in various embodiments, are carried out by one or moreprocessors under the control of computer-readable andcomputer-executable instructions that are stored on non-transitorycomputer-readable storage media. It is further appreciated that one ormore procedures described in flow diagram 700 may be implemented inhardware, or a combination of hardware with firmware and/or software.

As shown at procedure 710 of flow diagram 700, a prerecorded video filethat displays visual content is received. In one embodiment, theprerecorded video file is a short form prerecorded video file. In oneembodiment, the prerecorded video file is a looping prerecorded videofile.

At procedure 720, an executable experience associated with theprerecorded video file is received, wherein the executable experienceupon execution enables presentation of additional content associatedwith the prerecorded video file. In one embodiment, the executableexperience comprises an application. In one embodiment, the executableexperience comprises a media file. In one embodiment, the executableexperience comprises an instruction for executing an application locatedon the electronic device upon which the prerecorded video file isrendered.

At procedure 730, an identification of an interactive region of theprerecorded video file is received, wherein the interactive region ofthe prerecorded video file is associated with the executable experiencesuch that a user interaction with the interactive region executes theexecutable experience.

In some embodiments, as shown at procedure 740, at least onecustomization factor associated with the executable experience isreceived, wherein the at least one customization factor customizes theadditional content upon execution of the executable experience. In someembodiments, the at least one customization factor comprises at leastone of: a location, a user, a time day, and a date.

In some embodiments, the prerecorded video experience container includesmore than one executable experience. As shown at procedure 750, it isdetermined whether there are additional executable experiences toinclude within the prerecorded video experience container. If it isdetermined that there are more executable experiences to include withinthe prerecorded video experience container (e.g., as indicated by acreator of the prerecorded video experience container), flow diagram 700proceeds to procedure 720. If it is determined that there are no moreexecutable experiences to include within the prerecorded videoexperience container (e.g., as indicated by a creator of the prerecordedvideo experience container), flow diagram 700 proceeds to procedure 760.

At procedure 760, the prerecorded video file, the executableexperience(s), and the interactive region(s), are assembled into aprerecorded video experience container, wherein the prerecorded videoexperience container, when executed at an electronic device, displaysthe prerecorded video file and, responsive to identifying an interactionwith the interactive region, executes the executable experience. In someembodiments, the at least one customization factor is also assembledinto the prerecorded video experience container.

FIG. 8 illustrates a flow diagram 800 of an example method for creatinga prerecorded video experience container, according to variousembodiments. Procedures of this method may be described with referenceto elements and/or components of various figures described herein. It isappreciated that in some embodiments, the procedures may be performed ina different order than described, that some of the described proceduresmay not be performed, and/or that one or more additional procedures tothose described may be performed. Flow diagram 800 includes someprocedures that, in various embodiments, are carried out by one or moreprocessors under the control of computer-readable andcomputer-executable instructions that are stored on non-transitorycomputer-readable storage media. It is further appreciated that one ormore procedures described in flow diagram 800 may be implemented inhardware, or a combination of hardware with firmware and/or software.

As shown at procedure 805 of flow diagram 800, in one embodiment, aprerecorded video experience container is received. In one embodiment,the prerecorded video experience container is received via a messagingapplication. In one embodiment, the prerecorded video experiencecontainer is received via accessing a web site (e.g., the prerecordedvideo experience container is integrated into the website via anIframe).

At procedure 810, a prerecorded video file is displayed responsive to aninteraction with prerecorded video experience container (e.g., a userselection of the prerecorded video experience container). In oneembodiment, the prerecorded video file is a short form prerecorded videofile. In one embodiment, the prerecorded video file is a loopingprerecorded video file.

At procedure 820, an interaction with an interactive region of thedisplayed prerecorded video file is detected. It should be appreciatedthat there can be more than one interactive region of the prerecordedvideo file.

At procedure 830, an executable experience associated with theprerecorded video file and corresponding to the interactive region isexecuted. In one embodiment, as shown at procedure 832, the executableexperience is executed based at least in part on a customization factorassociated with the executable experience. In one embodiment, as shownat procedure 834, the executable experience is executed based at leastin part on a user profile of a user interacting with the prerecordedvideo file.

At procedure 840, additional content associated with the prerecordedvideo file is displayed in response to executing the executableexperience.

CONCLUSION

The examples set forth herein were presented in order to best explain,to describe particular applications, and to thereby enable those skilledin the art to make and use embodiments of the described examples.However, those skilled in the art will recognize that the foregoingdescription and examples have been presented for the purposes ofillustration and example only. Many aspects of the different exampleembodiments that are described above can be combined into newembodiments. The description as set forth is not intended to beexhaustive or to limit the embodiments to the precise form disclosed.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

Reference throughout this document to “one embodiment,” “certainembodiments,” “an embodiment,” “various embodiments,” “someembodiments,” or similar term means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, the appearances of suchphrases in various places throughout this specification are notnecessarily all referring to the same embodiment. Furthermore, theparticular features, structures, or characteristics of any embodimentmay be combined in any suitable manner with one or more other features,structures, or characteristics of one or more other embodiments withoutlimitation.

What is claimed is:
 1. A method, executed by one or more processors of amobile computing device including a display, comprising: receiving aprerecorded video file for displaying visual content, the prerecordedvideo file including an identification of an interactive region of theprerecorded video file and a time-related customization factor defininga time period for execution of an executable experience associated withthe prerecorded video file; displaying the prerecorded video file on thedisplay; receiving user selection of the interactive region; executing afirst executable experience on the mobile computing device based on afirst determination that a time of day or a particular day at the mobilecomputing device falls within the time period defined by thecustomization factor; and executing a second executable experience onthe mobile computing device based on a second determination that thetime of day or the particular day at the mobile computing device doesnot fall within the time period defined by the customization factor. 2.The method of claim 1 wherein the customization factor defines a date.3. The method of claim 2 wherein executing the first executableexperience presents an interface for purchasing a ticket to an event. 4.The method of claim 1 wherein executing the first executable experiencepresents a coupon that is redeemable at a business.
 5. The method ofclaim 1 wherein one or both of the first and second executableexperiences comprises instructions relating to an application stored onthe mobile computing device.
 6. The method of claim 1 furthercomprising: customizing one or both of the first and second executableexperiences according to a user profile of a user operating the mobilecomputing device.
 7. The method of claim 1 wherein one or both of thefirst and second executable experiences comprise a media file.
 8. Themethod of claim 1 wherein the customization factor further includes atleast one of a time of day, a day or a date.
 9. A non-transitorycomputer readable storage medium having computer readable program codestored thereon for causing a mobile computing device including a displayto perform a method comprising: receiving a prerecorded video file fordisplaying visual content, the prerecorded video file including anidentification of an interactive region of the prerecorded video fileand a time-related customization factor defining a time period forexecution of an executable experience associated with the prerecordedvideo file; displaying the prerecorded video file on the display;receiving user selection of the interactive region; executing a firstexecutable experience on the mobile computing device based on a firstdetermination that a time of day or a particular day at the mobilecomputing device falls within the time period defined by thecustomization factor; and executing a second executable experience onthe mobile computing device based on a second determination that thetime of day or the particular day at the mobile computing device doesnot fall within the time period defined by the customization factor. 10.The non-transitory computer readable storage medium of claim 9 whereinthe customization factor defines a date.
 11. The non-transitory computerreadable storage medium of claim 9 wherein executing the firstexecutable experience presents an interface for purchasing a ticket toan event.
 12. The non-transitory computer readable storage medium ofclaim 9 wherein executing the first executable experience presents acoupon that is redeemable at a business.
 13. The non-transitory computerreadable storage medium of claim 9 wherein one or both of the first andsecond executable experiences comprises instructions relating to anapplication stored on the mobile computing device.
 14. Thenon-transitory computer readable storage medium of claim 9 wherein themethod further comprises: customizing one or both of the first andsecond executable experiences according to a user profile of a useroperating the mobile computing device.
 15. The non-transitory computerreadable storage medium of claim 9 wherein one or both of the first andsecond executable experiences comprise a media file.
 16. Thenon-transitory computer readable storage medium of claim 9 wherein thecustomization factor further includes at least one of a time of day, aday or a date.
 17. A mobile computing device comprising: one or moreprocessors; a display; and a memory storing instructions for providingprerecorded video experience to a user of the mobile computing device,the instructions when executed by at least one processor among the oneor more processors, causes the mobile computing device to performoperations comprising: receiving a prerecorded video file for displayingvisual content, the prerecorded video file including an identificationof an interactive region of the prerecorded video file and atime-related customization factor defining a time period for executionof an executable experience associated with the prerecorded video file;displaying the prerecorded video file on the display; receiving userselection of the interactive region; executing a first executableexperience on the mobile computing device based on a first determinationthat a time of day or a particular day at the mobile computing devicefalls within the time period defined by the customization factor; andexecuting a second executable experience on the mobile computing devicebased on a second determination that the time of day or the particularday at the mobile computing device does not fall within the time perioddefined by the customization factor.
 18. The mobile computing device ofclaim 17 wherein executing the first executable experience presents aninterface for purchasing a ticket to an event.
 19. The mobile computingdevice of claim 17 wherein the customization factor defines a date. 20.The mobile computing device of claim 17 wherein executing the firstexecutable experience presents a coupon that is redeemable at abusiness.